Methods and apparatus to encode and decode audio for shopper location and advertisement presentation tracking

ABSTRACT

Methods and apparatus to encode and decode audio for shopper location and advertisement presentation tracking are disclosed. A method for tracking a shopper includes receiving a first audio signal at a first location with a decoder attached to a shopping implement, determining a first code encoded in the first audio signal, receiving a second audio signal at a second location with the decoder, determining a second code encoded in the first audio signal, and transmitting the first code and the second code to a data retrieval device.

RELATED APPLICATIONS

This application is a non-provisional application of U.S. Provisional Patent Application Ser. No. 61/118,268, filed Nov. 26, 2008, and entitled “AUDIO ENCODING/DECODING FOR USE IN SHOPPER LOCATION AND TRACKING AND ADVERTISEMENT PRESENTATION,” which is incorporated by reference in its entirety. This application incorporates by reference in its entirety U.S. patent application Ser. No. 12/249,619, filed Oct. 10, 2008, and entitled “METHODS AND APPARATUS TO PERFORM AUDIO WATERMARKING AND WATERMARK DETECTION AND EXTRACTION.”

FIELD OF THE DISCLOSURE

The present disclosure relates generally to media monitoring and, more particularly, audio encoding and decoding for use in shopper location and tracking advertisement presentation.

BACKGROUND

Identifying media information and, more specifically, audio streams (e.g., audio information) is useful for assessing audience exposure to television, radio, or any other media. For example, in television audience metering applications, a code may be inserted into the audio or video of media, wherein the code is later detected at monitoring sites when the media is presented (e.g., played at monitored households). The information payload of the code/watermark embedded into original signal can consist of unique source identification, time of broadcast, transactional or additional content metadata. Monitoring sites typically include locations such as, for example, households where the media consumption of audience members or audience member exposure to the media is monitored. For example, at a monitoring site, codes from the audio and/or video are captured and may be associated with audio or video streams of media associated with a selected channel, radio station, media source, etc. The collected codes may then be sent to a central data collection facility for analysis. However, the collection of data pertinent to media exposure or consumption need not be limited to in-home exposure or consumption.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic depiction of a broadcast audience measurement system employing a program identifying code added to the audio portion of a composite television signal.

FIG. 2 is a block diagram of an example encoder of FIG. 1.

FIG. 3 is a flow diagram illustrating an example encoding process that may be carried out by the example decoder of FIG. 2.

FIG. 4 is a flow diagram illustrating an example process that may be carried to generate a frequency index table used in conjunction with the code frequency selector of FIG. 2.

FIG. 5 is a chart illustrating critical band indices and how they correspond to short and long block sample indices.

FIG. 6 illustrates one example of selecting frequency components that will represent a particular information symbol.

FIGS. 7-9 are charts illustrating different example code frequency configurations that may be generated by the process of FIG. 4 and used in conjunction with the code frequency selector of FIG. 2.

FIG. 10 illustrates the frequency relationship between the audio encoding indices.

FIG. 11 is a block diagram of the example decoder of FIG. 1.

FIG. 12 is a flow diagram illustrating an example decoding process that may be carried out by the example encoder of FIG. 11.

FIG. 13 is a flow diagram of an example process that may be carried out to stack audio in the decoder of FIG. 11.

FIG. 14 is a flow diagram of an example process that may be carried out to determine a symbol encoded in an audio signal in the decoder of FIG. 11.

FIG. 15 is a flow diagram of an example process that may be carried out to process a buffer to identify messages in the decoder of FIG. 11.

FIG. 16 illustrates an example set of circular buffers that may store message symbols.

FIG. 17 illustrates an example set of pre-existing code flag circular buffers that may store message symbols.

FIG. 18 is a flow diagram of an example process that may be carried out to validate identified messages in the decoder of FIG. 11.

FIG. 19 illustrates an example filter stack that may store identified messages in the decoder of FIG. 11.

FIG. 20 is a block diagram illustrating an example situation in which multiple encoders and decoders may be used to perform customer tracking.

FIG. 21 is a block diagram illustrating an example technique by which audio may be mixed with a code signal in free space.

FIG. 22 is a block diagram illustrating an example technique by which embedded audio codes may be used to remotely control a target device.

FIG. 23 is a flowchart of an example process that may be performed to implement the decoder/logger of FIG. 20.

FIG. 24 is a flowchart of an example process that may be performed after the decoder/logger has logged one or more codes.

FIG. 25 is a flowchart of an example process that may implement the example code generator.

FIG. 26 is a flowchart of an example usage scenario for the system of FIG. 20.

FIG. 27 is a schematic illustration of an example processor platform that may be used and/or programmed to perform any or all of the processes or implement any or all of the example systems, example apparatus and/or example methods described herein.

DETAILED DESCRIPTION

The following description makes reference to audio encoding and decoding that is also commonly known as audio watermarking and watermark detection, respectively. It should be noted that in this context, audio may be any type of signal having a frequency falling within the normal human audibility spectrum. For example, audio may be speech, music, an audio portion of an audio and/or video program or work (e.g., a television program, a movie, an Internet video, a radio program, a commercial spot, etc.), a media program, noise, or any other sound.

In general, as described in detail below, the encoding of the audio inserts one or more codes or information (as known as watermarks) into the audio and, ideally, leaves the code inaudible to hearers of the audio. However, there may be certain situations in which the code may be audible to certain listeners. The codes that are embedded in audio may be of any suitable length and any suitable technique for assigning the codes to information may be selected.

As described below, the codes or information to be inserted into the audio may be converted into symbols that will be represented by code frequency signals to be embedded in the audio to represent the information. The code frequency signals include one or more code frequencies, wherein different code frequencies or sets of code frequencies are assigned to represent different symbols of information. Techniques for generating one or more tables mapping symbols to representative code frequencies such that symbols are distinguishable from one another at the decoder are also described. Any suitable encoding or error correcting technique may be used to convert codes into symbols.

By controlling the amplitude at which these code frequency signals are input into the native audio, the presence of the code frequency signals can be imperceptible to human hearing. Accordingly, in one example, masking operations based on the energy content of the native audio at different frequencies and/or the tonality or noise-like nature of the native audio are used to provide information upon which the amplitude of the code frequency signals is based.

Additionally, it is possible that an audio signal has passed through a distribution chain, where, for example, the content has passed from a content originator to a network distributor (e.g., NBC national) and further passed to a local content distributor (e.g., NBC in Chicago). As the audio signal passes through the distribution chain, one of the distributors may encode a watermark into the audio signal in accordance with the techniques described herein, thereby including in the audio signal an indication of that distributors identity or the time of distribution. The encoding described herein is very robust and, therefore, codes inserted into the audio signal are not easily removed. Accordingly, any subsequent distributors of the audio content may use techniques described herein to encode the previously encoded audio signal in a manner such that the code of the subsequent distributor will be detectable and any crediting due that subsequent distributor will be acknowledged.

Additionally, due to the repetition or partial repetition of codes within a signal, code detection can be improved by stacking messages and transforming the encoded audio signal into a signal having an accentuated code. As the audio signal is sampled at a monitored location, substantially equal sized blocks of audio samples are summed and averaged. This stacking process takes advantage of the temporal properties of the audio signal to cause the code signal to be accentuated within the audio signal. Accordingly, the stacking process, when used, can provide increased robustness to noise or other interference. For example, the stacking process may be useful when the decoding operation uses a microphone that might pick up ambient noise in addition to the audio signal output by a speaker.

A further technique to add robustness to the decoding operations described herein provides for validation of messages identified by a decoding operation. After messages are identified in an encoded audio signal, the messages are added to a stack. Subsequent repetitions of messages are then compared to identify matches. When a message can be matched to another message identified at the proper repetition interval, the messages are identified as validated. When a message can be partially matched to another message that has already been validated, the message is marked as partially validated and subsequent messages are used to identify parts of the message that may have been corrupted. According to this example validation technique, messages are only output from the decoder if they can be validated. Such a technique prevents errors in messages caused by interference and/or detection errors.

The following examples pertain generally to encoding an audio signal with information, such as a code, and obtaining that information from the audio via a decoding process. The following example encoding and decoding processes may be used in several different technical applications to convey information from one place to another.

The example encoding and decoding processes described herein may be used to perform broadcast identification. In such an example, before a work is broadcast, that work is encoded to include a code indicative of the source of the work, the broadcast time of the work, the distribution channel of the work, or any other information deemed relevant to the operator of the system. When the work is presented (e.g., played through a television, a radio, a computing device, or any other suitable device), persons in the area of the presentation are exposed not only to the work, but, unbeknownst to them, are also exposed to the code embedded in the work. Thus, persons may be provided with decoders that operate on a microphone-based platform so that the work may be obtained by the decoder using free-field detection and processed to extract codes therefrom. The codes may then be logged and reported back to a central facility for further processing. The microphone-based decoders may be dedicated, stand-alone devices, or may be implemented using cellular telephones or any other types of devices having microphones and software to perform the decoding and code logging operations. Alternatively, wire-based systems may be used whenever the work and its attendant code may be picked up via a hard wired connection.

The example encoding and decoding processes described herein may be used, for example, in tracking and/or forensics related to audio and/or video works by, for example, marking copyrighted audio and/or associated video content with a particular code. The example encoding and decoding processes may be used to implement a transactional encoding system in which a unique code is inserted into a work when that work is purchased by a consumer. Thus, allowing a media distribution to identify a source of a work. The purchasing may include a purchaser physically receiving a tangible media (e.g., a compact disk, etc.) on which the work is included, or may include downloading of the work via a network, such as the Internet. In the context of transactional encoding systems, each purchaser of the same work receives the work, but the work received by each purchaser is encoded with a different code. That is, the code inserted in the work may be personal to the purchaser, wherein each work purchased by that purchaser includes that purchaser's code. Alternatively, each work may be may be encoded with a code that is serially assigned.

Furthermore, the example encoding and decoding techniques described herein may be used to carry out control functionality by hiding codes in a steganographic manner, wherein the hidden codes are used to control target devices programmed to respond to the codes. For example, control data may be hidden in a speech signal, or any other audio signal. A decoder in the area of the presented audio signal processes the received audio to obtain the hidden code. After obtaining the code, the target device takes some predetermined action based on the code. This may be useful, for example, in the case of changing advertisements within stores based on audio being presented in the store, etc. For example, scrolling billboard advertisements within a store may be synchronized to an audio commercial being presented in the store through the use of codes embedded in the audio commercial.

An example encoding and decoding system 100 is shown in FIG. 1. The example system 100 may be, for example, a television audience measurement system, which will serve as a context for further description of the encoding and decoding processes described herein. The example system 100 includes an encoder 102 that adds a code or information 103 to an audio signal 104 to produce an encoded audio signal. The information 103 may be any selected information. For example, in a media monitoring context, the information 103 may be representative of an identity of a broadcast media program such as a television broadcast, a radio broadcast, or the like. Additionally, the information 103 may include timing information indicative of a time at which the information 103 was inserted into audio or a media broadcast time. Alternatively, the code may include control information that is used to control the behavior of one or more target devices.

The audio signal 104 may be any form of audio including, for example, voice, music, noise, commercial advertisement audio, audio associated with a television program, live performance, etc. In the example of FIG. 1, the encoder 102 passes the encoded audio signal to a transmitter 106. The transmitter 106 transmits the encoded audio signal along with any video signal 108 associated with the encoded audio signal. While, in some instances, the encoded audio signal may have an associated video signal 108, the encoded audio signal need not have any associated video.

In one example, the audio signal 104 is a digitized version of an analog audio signal, wherein the analog audio signal has been sampled at 48 kilohertz (KHz). As described below in detail, two seconds of audio, which correspond to 96,000 audio samples at the 48 KHz sampling rate, may be used to carry one message, which may be a synchronization message and 49 bits of information. Using an encoding scheme of 7 bits per symbol, the message requires transmission of eight symbols of information. Alternatively, in the context of overwriting described below, one synchronization symbol is used and one information symbol conveying one of 128 states follows the synchronization symbol. As described below in detail, according to one example, one 7-bit symbol of information is embedded in a long block of audio samples, which corresponds to 9216 samples. In one example, such a long block includes 36 overlapping short blocks of 256 samples, wherein in a 50% overlapping block 256 of the samples are old and 256 samples are new.

Although the transmit side of the example system 100 shown in FIG. 1 shows a single transmitter 106, the transmit side may be much more complex and may include multiple levels in a distribution chain through which the audio signal 104 may be passed. For example, the audio signal 104 may be generated at a national network level and passed to a local network level for local distribution. Accordingly, although the encoder 102 is shown in the transmit lineup prior to the transmitter 106, one or more encoders may be placed throughout the distribution chain of the audio signal 104. Thus, the audio signal 104 may be encoded at multiple levels and may include embedded codes associated with those multiple levels. Further details regarding encoding and example encoders are provided below.

The transmitter 106 may include one or more of a radio frequency (RF) transmitter that may distribute the encoded audio signal through free space propagation (e.g., via terrestrial or satellite communication links) or a transmitter used to distribute the encoded audio signal through cable, fiber, etc. In one example, the transmitter 106 may be used to broadcast the encoded audio signal throughout a broad geographical area. In other cases, the transmitter 106 may distribute the encoded audio signal through a limited geographical area. The transmission may include up-conversion of the encoded audio signal to radio frequencies to enable propagation of the same. Alternatively, the transmission may include distributing the encoded audio signal in the form of digital bits or packets of digital bits that may be transmitted over one or more networks, such as the Internet, wide area networks, or local area networks. Thus, the encoded audio signal may be carried by a carrier signal, by information packets or by any suitable technique to distribute the audio signals.

When the encoded audio signal is received by a receiver 110, which, in the media monitoring context, may be located at a statistically selected metering site 112, the audio signal portion of the received program signal is processed to recover the code, even though the presence of that code is imperceptible (or substantially imperceptible) to a listener when the encoded audio signal is presented by speakers 114 of the receiver 110. To this end, a decoder 116 is connected either directly to an audio output 118 available at the receiver 110 or to a microphone 120 placed in the vicinity of the speakers 114 through which the audio is reproduced. The received audio signal can be either in a monaural or stereo format. Further details regarding decoding and example decoders are provided below.

Audio Encoding

As explained above, the encoder 102 inserts one or more inaudible (or substantially inaudible) codes into the audio 104 to create encoded audio. One example encoder 102 is shown in FIG. 2. In one implementation, the example encoder 102 of FIG. 2 may be implemented using, for example, a digital signal processor programmed with instructions to implement an encoding lineup 202, the operation of which is affected by the operations of a prior code detector 204 and a masking lineup 206, either or both of which can be implemented using a digital signal processor programmed with instructions. Of course, any other implementation of the example encoder 102 is possible. For example, the encoder 102 may be implemented using one or more processors, programmable logic devices, or any suitable combination of hardware, software, and firmware.

In general, during operation, the encoder 102 receives the audio 104 and the prior code detector 204 determines if the audio 104 has been previously encoded with information, which will make it difficult for the encoder 102 to encode additional information into the previously encoded audio. For example, a prior encoding may have been performed at a prior location in the audio distribution chain (e.g., at a national network level). The prior code detector 204 informs the encoding lineup 202 as to whether the audio has been previously encoded. The prior code detector 204 may be implemented by a decoder as described herein.

The encoding lineup 202 receives the information 103 and produces code frequency signals based thereon and combines the code frequency signal with the audio 104. The operation of the encoding lineup 202 is influenced by the output of the prior code detector 204. For example, if the audio 104 has been previously encoded and the prior code detector 204 informs the encoding lineup 202 of this fact, the encoding lineup 202 may select an alternate message that is to be encoded in the audio 104 and may also alter the details by which the alternate message is encoded (e.g., different temporal location within the message, different frequencies used to represent symbols, etc.).

The encoding lineup 202 is also influenced by the masking lineup 206. In general, the masking lineup 206 processes the audio 104 corresponding to the point in time at which the encoding lineup 202 wants to encode information and determines the amplitude at which the encoding should be performed. As described below, the masking lineup 206 may output a signal to control code frequency signal amplitudes to keep the code frequency signal below the threshold of human perception.

As shown in the example of FIG. 2, the encoding lineup includes a message generator 210, a symbol selector 212, a code frequency selector 214, a synthesizer 216, an inverse Fourier transform 218, and a combiner 220. The message generator 210 is responsive to the information 103 and outputs messages having the format generally shown at reference numeral 222. The information 103 provided to the message generator may be the current time, a television or radio station identification, a program identification, etc. In one example, the message generator 210 may output a message every two seconds. Of course, other messaging intervals are possible.

In one example, the message format 222 representative of messages output from the message generator 210 includes a synchronization symbol 224. The synchronization symbol 224 is used by decoders, examples of which are described below, to obtain timing information indicative of the start of a message. Thus, when a decoder receives the synchronization symbol 224, that decoder expects to see additional information following the synchronization symbol 224.

In the example message format 222 of FIG. 2, the synchronization symbol 224, is followed by 42 bits of message information 226. This information may include a binary representation of a station identifier and coarse timing information. In one example, the timing information represented in the 42 bits of message information 226 changes every 64 seconds, or 32 message intervals. Thus, the 42 bits of message information 226 remain static for 64 seconds. The seven bits of message information 228 may be high resolution time that increments every two seconds.

The message format 222 also includes pre-existing code flag information 230. However, the pre-existing code flag information 230 is only selectively used to convey information. When the prior code detector 204 informs the message generator 210 that the audio 104 has not been previously encoded, the pre-existing code flag information 230 is not used. Accordingly, the message output by the message generator only includes the synchronization symbol 224, the 42 bits of message information 226, and the seven bits of message information 228; the pre-existing code flag information 230 is blank or filled by unused symbol indications. In contrast, when the prior code detector 204 provides to the message generator 210 an indication that the audio 104 into which the message information is to be encoded has previously been encoded, the message generator 210 will not output the synchronization symbol 224, the 42 bits of message information 226, or the seven bits of message information 228. Rather, the message generator 210 will utilize only the pre-existing code flag information 230. In one example, the pre-existing code flag information will include a pre-existing code flag synchronization symbol to signal that pre-existing code flag information is present. The pre-existing code flag synchronization symbol is different from the synchronization symbol 224 and, therefore, can be used to signal the start of pre-existing code flag information. Upon receipt of the pre-existing code flag synchronization symbol, a decoder can ignore any prior-received information that aligned in time with a synchronization symbol 224, 42 bits of message information 226, or seven bits of message information 228. To convey information, such as a channel indication, a distribution identification, or any other suitable information, a single pre-existing code flag information symbol follows the pre-existing code flag synchronization symbol. This pre-existing code flag information may be used to provide for proper crediting in an audience monitoring system.

The output from the message generator 210 is passed to the symbol selector 212, which selects representative symbols. When the synchronization symbol 224 is output, the symbol selector may not need to perform any mapping because the synchronization symbol 224 is already in symbol format. Alternatively, if bits of information are output from the message generator 210, the symbol selector may use straight mapping, wherein, for example seven bits output from the message generator 210 are mapped to a symbol having the decimal value of the seven bits. For example, if a value of 1010101 is output from the message generator 210, the symbol selector may map those bits to the symbol 85. Of course other conversions between bits and symbols may be used. In certain examples, redundancy or error encoding may be used in the selection of symbols to represent bits. Additionally, any other suitable number of bits than seven may be selected to be converted into symbols. The number of bits used to select the symbol may be determined based on the maximum symbol space available in the communication system. For example, if the communication system can only transmit one of four symbols at a time, then only two bits from the message generator 210 would be converted into symbols at a time.

The symbols from the symbol selector 212 are passed to the code frequency selector 214 that selects code frequencies that are used to represent the symbol. The symbol selector 212 may include one or more look up tables (LUTs) 232 that may be used to map the symbols into code frequencies that represent the symbols. That is, a symbol is represented by a plurality of code frequencies that the encoder 102 emphasizes in the audio to form encoded audio that is transmitted. Upon receipt of the encoded audio, a decoder detects the presence of the emphasized code frequencies and decodes the pattern of emphasized code frequencies into the transmitted symbol. Thus, the same LUT selected at the encoder 210 for selecting the code frequencies needs to be used in the decoder. One example LUT is described in conjunction with FIGS. 3-5. Additionally, example techniques for generating LUTs are provided in conjunction with FIGS. 7-9.

The code frequency selector 214 may select any number of different LUTs depending of various criteria. For example, a particular LUT or set of LUTs may be used by the code frequency selector 214 in response to the prior receipt of a particular synchronization symbol. Additionally, if the prior code detector 204 indicates that a message was previously encoded into the audio 104, the code frequency selector 214 may select a lookup table that is unique to pre-existing code situations to avoid confusion between frequencies used to previously encode the audio 104 and the frequencies used to include the pre-existing code flag information.

An indication of the code frequencies that are selected to represent a particular symbol is provided to the synthesizer 216. The synthesizer 216 may store, for each short block constituting a long block, three complex Fourier coefficients representative of each of the possible code frequencies that the code frequency selector 214 will indicate. These coefficients represent the transform of a windowed sinusoidal code frequency signal whose phase angle corresponds to the starting phase angle of code sinusoid in that short block.

While the foregoing describes an example code synthesizer 208 that generates sine waves or data representing sine waves, other example implementations of code synthesizers are possible. For example, rather than generating sine waves, another example code synthesizer 208 may output Fourier coefficients in the frequency domain that are used to adjust amplitudes of certain frequencies of audio provided to the combiner 220. In this manner, the spectrum of the audio may be adjusted to include the requisite sine waves.

The three complex amplitude-adjusted Fourier coefficients corresponding to the symbol to be transmitted are provided from the synthesizer 216 to the inverse Fourier transform 218, which converts the coefficients into time-domain signals having the prescribed frequencies and amplitudes to allow their insertion into the audio to convey the desired symbols are coupled to the combiner 220. The combiner 220 also receives the audio. In particular, the combiner 220 inserts the signals from the inverse Fourier transform 218 into one long block of audio samples. As described above, for a given sampling rate of 48 KHz, a long block is 9216 audio samples. In the provided example, the synchronization symbol and 49 bits of information require a total of eight long blocks. Because each long block is 9216 audio samples, only 73,728 samples of audio 104 are needed to encode a given message. However, because messages begin every two seconds, which is every 96,000 audio samples, there will be many samples at the end of the 96,000 audio samples that are not encoded. The combining can be done in the digital domain, or in the analog domain.

However, in the case of a pre-existing code flag, the pre-existing code flag is inserted into the audio 104 after the last symbol representing the previously inserted seven bits of message information. Accordingly, insertion of the pre-existing code flag information begins at sample 73,729 and runs for two long blocks, or 18,432 samples. Accordingly, when pre-existing code flag information is used, fewer of the 96,000 audio samples 104 will be unencoded.

The masking lineup 206 includes an overlapping short block maker that makes short blocks of 512 audio samples, wherein 256 of the samples are old and 256 samples are new. That is, the overlapping short block maker 240 makes blocks of 512 samples, wherein 256 samples are shifted into or out of the buffer at one time. For example, when a first set of 256 samples enters the buffer, the oldest 256 samples are shifted out of the buffer. On a subsequent iteration, the first set of 256 samples is shifted to a latter position of the buffer and 256 samples are shifted into the buffer. Each time a new short block is made by shifting in 256 new samples and removing the 256 oldest samples, the new short block is provided to a masking evaluator 242. The 512 sample block output from the overlapping short block maker 240 is multiplied by a suitable window function such that an “overlap-and-add” operation will restore the audio samples to their correct value at the output. A synthesized code signal to be added to an audio signal is also similarly windowed to prevent abrupt transitions at block edges when there is a change in code amplitude from one 512-sample block to the next overlapped 512-sample block. These transitions if present create audible artifacts.

The masking evaluator 242 receives samples of the overlapping short block (e.g., 512 samples) and determines an ability of the same to hide code frequencies to human hearing. That is, the masking evaluator determines if code frequencies can be hidden within the audio represented by the short block by evaluating each critical band of the audio as a whole to determine its energy and determining the noise-like or tonal-like attributes of each critical band and determining the sum total ability of the critical bands to mask the code frequencies. According to the illustrated example, the bandwidth of the critical bands increases with frequency. If the masking evaluator 242 determines that code frequencies can be hidden in the audio 104, the masking evaluator 204 indicates the amplitude levels at which the code frequencies can be inserted within the audio 104, while still remaining hidden and provides the amplitude information to the synthesizer 216.

In one example, the masking evaluator 242 conducts the masking evaluation by determining a maximum change in energy E_(b) or a masking energy level that can occur at any critical frequency band without making the change perceptible to a listener. The masking evaluation carried out by the masking evaluator 242 may be carried out as outlined in the Moving Pictures Experts Group—Advanced Audio Encoding (MPEG-AAC) audio compression standard ISO/IEC 13818-7:1997, for example. The acoustic energy in each critical band influences the masking energy of its neighbors and algorithms for computing the masking effect are described in the standards document such as ISO/IEC 13818-7:1997. These analyses may be used to determine for each short block the masking contribution due to tonality (e.g., how much the audio being evaluated is like a tone) as well as noise like (i.e., how much the audio being evaluated is like noise) features. Further analysis can evaluate temporal masking that extends masking ability of the audio over short time, typically, for 50-100 milliseconds (ms). The resulting analysis by the masking evaluator 242 provides a determination, on a per critical band basis, the amplitude of a code frequency that can be added to the audio 104 without producing any noticeable audio degradation (e.g., without being audible).

Because a 256 sample block will appear in both the beginning of one short block and the end of the next short block and, thus, will be evaluated two times by the masking evaluator 242, the masking evaluator makes two masking evaluations including the 256 sample block. The amplitude indication provided to the synthesizer 216 is a composite of those two evaluations including that 256 sample block and the amplitude indication is timed such that the amplitude of the code inserted into the 256 samples is timed with those samples arriving at the combiner 220.

Referring now to FIGS. 3-5, an example LUT 232 is shown that includes one column representing symbols 302 and seven columns 304, 306, 308, 310, 312, 314, 316 representing numbered code frequency indices. The LUT 232 includes 129 rows, 128 of which are used to represent data symbols and one of which is used to represent a synchronization symbol. Because the LUT 232 includes 128 different data symbols, data may be sent at a rate of seven bits per symbol. The frequency indices in the table may range from 180-656 and are based on a long block size of 9216 samples and a sampling rate of 48 KHz. Accordingly, the frequencies corresponding to these indices range between 937.5 Hz and 3126.6 Hz, which falls into the humanly audible range. Of course, other sampling rates and frequency indices may be selected. A description of a process to generate a LUT, such as the table 232 is provided in conjunction with FIGS. 7-9.

In one example operation of the code frequency selector 214, a symbol of 25 (e.g., a binary value of 0011001) is received from the symbol selector 212. The code frequency selector 214 accesses the LUT 232 and reads row 25 of the symbol column 302. From this row, the code frequency selector reads that code frequency indices 217, 288, 325, 403, 512, 548, and 655 are to be emphasized in the audio 104 to communicate the symbol 25 to the decoder. The code frequency selector 214 then provides an indication of these indices to the synthesizer 216, which synthesizes the code signals by outputting Fourier coefficients corresponding to these indices.

The combiner 220 receives both the output of the code synthesizer 208 and the audio 104 and combines them to form encoded audio. The combiner 220 may combine the output of the code synthesizer 208 and the audio 104 in an analog or digital form. If the combiner 220 performs a digital combination, the output of the code synthesizer 208 may be combined with the output of the sampler 202, rather than the audio 104 that is input to the sampler 202. For example, the audio block in digital form may be combined with the sine waves in digital form. Alternatively, the combination may be carried out in the frequency domain, wherein frequency coefficients of the audio are adjusted in accordance with frequency coefficients representing the sine waves. As a further alternative, the sine waves and the audio may be combined in analog form. The encoded audio may be output from the combiner 220 in analog or digital form. If the output of the combiner 220 is digital, it may be subsequently converted to analog form before being coupled to the transmitter 106.

An example encoding process 600 is shown in FIG. 6. The example process 600 may be carried out by the example encoder 102 of FIG. 2, or by any other suitable encoder. The example process 600 begins when audio samples to be encoded are received (block 602). The process 600 then determines if the received samples have been previously encoded (block 604). This determination may be carried out, for example, by the prior code detector 204 of FIG. 2, or by any suitable decoder configured to examine the audio to be encoded for evidence of a prior encoding.

If the received samples have not been previously encoded (block 604), the process 600 generates a communication message (block 606), such as a communication message having the format shown in FIG. 2 at reference numeral 222. In one particular example, when the audio has not been previously encoded, the communication message may include a synchronization portion and one or more portions including data bits. The communication message generation may be carried out, for example, by the message generator 210 of FIG. 2.

The communication message is then mapped into symbols (block 608). For example, the synchronization information need not be mapped into a symbol if the synchronization information is already a symbol. In another example, if a portion of the communication message is a series of bits, such bits or groups of bits may be represented by one symbol. As described above in conjunction with the symbol selector 212, which is one manner in which the mapping (block 608) may be carried out, one or more tables or encoding schemes may be used to convert bits into symbols. For example, some techniques may include the use of error correction coding, or the like, to increase message robustness through the use of coding gain. In one particular example implementation having a symbol space sized to accommodate 128 data symbols, seven bits may be converted into one symbol. Of course, other numbers of bits may be processed depending on many factors including available symbol space, error correction encoding, etc.

After the communication symbols have been selected (block 608), the process 600 selects a LUT that will be used to determine the code frequencies that will be used to represent each symbol (block 610). In one example, the selected LUT may be the example LUT 232 of FIGS. 3-5, or may be any other suitable LUT. Additionally, the LUT may be any LUT generated as described in conjunction with FIGS. 7-9. The selection of the LUT may be based on a number of factors including the synchronization symbol that is selected during the generation of the communication message (block 606).

After the symbols have been generated (block 608) and the LUT is selected (block 610), the symbols are mapped into code frequencies using the selected LUT (block 612). In one example in which the LUT 232 of FIG. 3-5 is selected, a symbol of, for example, 35 would be mapped to the frequency indices 218, 245, 360, 438, 476, 541, and 651. The data space in the LUT is between symbol 0 and symbol 127 and symbol 128, which uses a unique set of code frequencies that do not match any other code frequencies in the table, is used to indicate a synchronization symbol. The LUT selection (block 610) and the mapping (block 612) may be carried out by, for example, the code frequency selector 214 of FIG. 2. After the code frequencies are selected, an indication of the same is provided to, for example, the synthesizer 216 of FIG. 2.

Code signals including the code frequencies are then synthesized (block 614) at amplitudes according to a masking evaluation, which is described in conjunction with blocks 240 and 242 or FIG. 2, and is described in conjunction with the process 600 below. In one example, the synthesis of the code frequency signals may be carried out by providing appropriately scaled Fourier coefficients to an inverse Fourier process. In one particular example, three Fourier coefficients may be output to represent each code frequency in the code frequency signals. Accordingly, the code frequencies may be synthesized by the inverse Fourier process in a manner in which the synthesized frequencies are windowed to prevent spill over into other portions of the signal into which the code frequency signals are being embedded. One example configuration that may be used to carry out the synthesis of block 614 is shown at blocks 216 and 218 of FIG. 2. Of course other implementations and configurations are possible.

After the code signals including the code frequencies have been synthesized, they are combined with the audio samples (block 616). As described in conjunction with FIG. 2, the combination of the code signals and the audio is such that one symbol is inserted into each long block of audio samples. Accordingly, to communicate one synchronization symbol and 49 data bits, information is encoded into eight long blocks of audio information: one long block for the synchronization symbol and one long block for each seven bits of data (assuming seven bits/symbol encoding). The messages are inserted into the audio at two second intervals. Thus, the eight long blocks of audio immediately following the start of a message may be encoded with audio and the remaining long blocks that make up the balance of the two second of audio may be unencoded.

The insertion of the code signal into the audio may be carried out by adding samples of the code signal to samples of the host audio signal, wherein such addition is done in the analog domain or in the digital domain. Alternatively, with proper frequency alignment and registration, frequency components of the audio signal may be adjusted in the frequency domain and the adjusted spectrum converted back into the time domain.

The foregoing described the operation of the process 600 when the process determined that the received audio samples have not been previously encoded (block 604). However, in situations in which a portion of media has been through a distribution chain and encoded as it was processed, the received samples of audio processed at block 604 already include codes. For example, a local television station using a courtesy news clip from CNN in a local news broadcast might not get viewing credit based on the prior encoding of the CNN clip. As such, additional information is added to the local news broadcast in the form of pre-existing code flag information. If the received samples of audio have been previously encoded (block 604), the process generates pre-existing code flag information (block 618). The pre-existing code flag information may include the generation of a pre-existing code flag synchronization symbol and, for example, the generation of seven bits of data, which will be represented by a single data symbol. The data symbol may represent a station identification, a time, or any other suitable information. For example, a media monitoring site (MMS) may be programmed to detect the pre-existing code flag information to credit the station identified therein.

After the pre-existing code flag information has been generated (block 618), the process 600 selects the pre-existing code flag LUT that will be used to identify code frequencies representative of the pre-existing code flag information (block 620). In one example, the pre-existing code flag LUT may be different than other LUTs used in non-pre-existing code conditions. In one particular example, the pre-existing code flag synchronization symbol may be represented by the code frequencies 220, 292, 364, 436, 508, 580, and 652.

After the pre-existing code flag information is generated (block 618) and the pre-existing code flag LUT is selected (block 620), the pre-existing code flag symbols are mapped to code frequencies (block 612), and the remainder of the processing follows as previously described.

Sometime before the code signal is synthesized (block 614), the process 600 conducts a masking evaluation to determine the amplitude at which the code signal should be generated so that it still remains inaudible or substantially inaudible to human hearers. Accordingly, the process 600 generates overlapping short blocks of audio samples, each containing 512 audio samples (block 622). As described above, the overlapping short blocks include 50% old samples and 50% newly received samples. This operation may be carried out by, for example, the overlapping short block maker 240 of FIG. 2.

After the overlapping short blocks are generated (block 622), masking evaluations are performed on the short blocks (block 624). For example, this may be carried out as described in conjunction with block 242 of FIG. 2. The results of the masking evaluation are used by the process 600 at block 614 to determine the amplitude of the code signal to be synthesized. The overlapping short block methodology may yield two masking evaluation for a particular 256 samples of audio (one when the 256 samples are the “new samples,” and one when the 256 samples are the “old samples”), the result provided to block 614 of the process 600 may be a composite of these masking evaluations. Of course, the timing of the process 600 is such that the masking evaluations for a particular block of audio are used to determine code amplitudes for that block of audio.

Lookup Table Generation

A system 700 for populating one or more LUTs with code frequencies corresponding to symbols may be implemented using hardware, software, combinations of hardware and software, firmware, or the like. The system 700 of FIG. 7 may be used to generate any number of LUTs, such as the LUT of FIGS. 3-5. The system 700 which operates as described below in conjunction with FIG. 7 and FIG. 8, results in a code frequency index LUT, wherein: (1) two symbols of the table are represented by no more than one common frequency index, (2) not more than one of the frequency indices representing a symbol reside in one audio critical band as defined by the MPEG-AA compression standard ISO/IEC 13818-7:1997, and (3) code frequencies of neighboring critical bands are not used to represent a single symbol. Criteria number 3 helps to ensure that audio quality is not compromised during the audio encoding process.

A critical band pair definer 702 defines a number (P) of critical band pairs. For example, referring to FIG. 9, a table 900 includes columns representing AAC critical band indices 902, short block indices 904 in the range of the AAC indices, and long block indices 906 in the range of the AAC indices. In one example, the value of P may be seven and, thus, seven critical band pairs are formed from the AAC indices (block 802). FIG. 10 shows the frequency relationship between the AAC indices. According to one example, as shown at reference numeral 1002 in FIG. 10 wherein frequencies of critical band pairs are shown as separated by dotted lines, AAC indices may be selected into pairs as follows: five and six, seven and eight, nine and ten, eleven and twelve, thirteen and fourteen, fifteen and sixteen, and seventeen and seventeen. The AAC index of seventeen includes a wide range of frequencies and, therefore, index 17 is shown twice, once for the low portion and once for the high portion.

A frequency definer 704 defines a number of frequencies (N) that are selected for use in each critical band pair. In one example, the value of N is sixteen, meaning that there are sixteen data positions in the combination of the critical bands that form each critical band pair. Reference numeral 1004 in FIG. 10 identifies the seventeen frequency positions are shown. The circled position four is reserved for synchronization information and, therefore, is not used for data.

A number generator 706 defines a number of frequency positions in the critical band pairs defined by the critical band pair definer 702. In one example the number generator 706 generates all NP, P-digit numbers. For example, if N is 16 and P is 7, the process generates the numbers 0 through 268435456, but may do so in base 16 hexadecimal, which would result in the values 0 through 10000000.

A redundancy reducer 708 then eliminates all number from the generated list of numbers sharing more than one common digit between them in the same position. This ensures compliance with criteria (1) above because, as described below, the digits will be representative of the frequencies selected to represent symbols. An excess reducer 710 may then further reduce the remaining numbers from the generated list of numbers to the number of needed symbols. For example, if the symbol space is 129 symbols, the remaining numbers are reduced to a count of 129. The reduction may be carried out at random, or by selecting remaining numbers with the greatest Euclidean distance, or my any other suitable data reduction technique. In another example, the reduction may be carried out in a pseudorandom manner.

After the foregoing reductions, the count of the list of numbers is equal to the number of symbols in the symbol space. Accordingly, a code frequency definer 712 defines the remaining numbers in base P format to represent frequency indices representative of symbols in the critical band pairs. For example, referring to FIG. 10, the hexadecimal number F1E4B0F is in base 16, which matches P. The first digit of the hexadecimal number maps to a frequency component in the first critical band pair, the second digit to the second critical band pair, and so on. Each digit represents the frequency index that will be used to represent the symbol corresponding to the hexadecimal number F1E4B0F.

Using the first hexadecimal number as an example of mapping to a particular frequency index, the decimal value of Fh is 15. Because position four of each critical band pair is reserved for non-data information, the value of any hexadecimal digit greater than four is incremented by the value of one decimal. Thus, the 15 becomes a 16. The 16 is thus designated (as shown with the asterisk in FIG. 10) as being the code frequency component in the first critical band pair to represent the symbol corresponding to the hexadecimal number F1E4B0F. Though not shown in FIG. 10, the index 1 position (e.g., the second position from the far left in the critical band 7 would be used to represent the hexadecimal number F1E4B0F.

A LUT filler 714 receives the symbol indications and corresponding code frequency component indications from the code frequency definer 712 and fills this information into a LUT.

An example code frequency index table generation process 800 is shown in FIG. 8. The process 800 may be implemented using the system of FIG. 7, or any other suitable configuration. The process 800 of FIG. 8 may be used to generate any number of LUTs, such as the LUT of FIGS. 3-5. While one example process 800 is shown, other processes may be used. The result of the process 800 is a code frequency index LUT, wherein: (1) two symbols of the table are represented by no more than one common frequency index, (2) not more than one of the frequency indices representing a symbol reside in one audio critical band as defined by the MPEG-AA compression standard ISO/IEC 13818-7:1997, and (3) code frequencies of neighboring critical bands are not used to represent a single symbol. Criteria number 3 helps to ensure that audio quality is not compromised during the audio encoding process.

The process 800 begins by defining a number (P) of critical band pairs. For example, referring to FIG. 9, a table 900 includes columns representing AAC critical band indices 902, short block indices 904 in the range of the AAC indices, and long block indices 906 in the range of the AAC indices. In one example, the value of P may be seven and, thus, seven critical band pairs are formed from the AAC indices (block 802). FIG. 10 shows the frequency relationship between the AAC indices. According to one example, as shown at reference numeral 1002 in FIG. 10 wherein frequencies of critical band pairs are shown as separated by dotted lines, AAC indices may be selected into pairs as follows: five and six, seven and eight, nine and ten, eleven and twelve, thirteen and fourteen, fifteen and sixteen, and seventeen and seventeen. The AAC index of seventeen includes a wide range of frequencies and, therefore, index 17 is shown twice, once for the low portion and once for the high portion.

After the band pairs have been defined (block 802), a number of frequencies (N) is selected for use in each critical band pair (block 804). In one example, the value of N is sixteen, meaning that there are sixteen data positions in the combination of the critical bands that form each critical band pair. As shown in FIG. 10 as reference numeral 1004, the seventeen frequency positions are shown. The circled position four is reserved for synchronization information and, therefore, is not used for data.

After the number of critical band pairs and the number of frequency positions in the pairs is defined, the process 800 generates all NP, P-digit numbers with no more than one hexadecimal digit in common (block 806). For example, if N is 16 and P is 7, the process generates the numbers 0 through 268435456, but may do so in base 16 hexadecimal, which would results in 0 through FFFFFFF, but does not include the numbers that share more than one common hexadecimal digit. This ensures compliance with criteria (1) above because, as described below, the digits will be representative of the frequencies selected to represent symbols.

According to an example process for determining a set of numbers that comply with criteria (1) above (and any other desired criteria), the numbers in the range from 0 to NP−1 are tested. First, the value corresponding to zero is stored as the first member of the result set R. Then, the numbers from 1 to NP−1 are selected for analysis to determine if they meet criteria (1) when compared to the members of R. Each number that meets criteria (1) when compared against all the current entries in R is added to the result set. In particular, according to the example process, in order to test a number K, each hexadecimal digit of interest in K is compared to the corresponding hexadecimal digit of interest in an entry M from the current result set. In the 7 comparisons not more than one hexadecimal digit of K should equal the corresponding hexadecimal digit of M. If, after comparing K against all numbers currently in the result set, no member of the latter has more than one common hexadecimal digit, then K is added to the result set R. The algorithm iterates through the set of possible numbers until all values meeting criteria (1) have been identified.

While the foregoing describes an example process for determining a set of numbers that meets criteria (1), any process or algorithm may be used and this disclosure is not limited to the process described above. For example, a process may use heuristics, rules, etc. to eliminate numbers from the set of numbers before iterating throughout the set. For example, all of the numbers where the relevant bits start with two 0's, two 1's, two 2's, etc. and end with two 0's, two 1's, two 2's, etc. could immediately be removed because they will definitely have a hamming distance less than 6. Additionally or alternatively, an example process may not iterate through the entire set of possible numbers. For example, a process could iterate until enough numbers are found (e.g., 128 numbers when 128 symbols are desired). In another implementation, the process may randomly select a first value for inclusion in the set of possible values and then may search iteratively or randomly through the remaining set of numbers until a value that meets the desired criteria (e.g., criteria (1)) is found.

The process 800 then selects the desired numbers from the generated values (block 810). For example, if the symbol space is 129 symbols, the remaining numbers are reduced to a count of 129. The reduction may be carried out at random, or by selecting remaining numbers with the greatest Euclidean distance, or my any other suitable data reduction technique.

After the foregoing reductions, the count of the list of numbers is equal to the number of symbols in the symbol space. Accordingly, the remaining numbers in base P format are defined to represent frequency indices representative of symbols in the critical band pairs (block 812). For example, referring to FIG. 10, the hexadecimal number F1E4B0F is in base 16, which matches P. The first digit of the hexadecimal number maps to a frequency component in the first critical band pair, the second digit to the second critical band pair, and so on. Each digit represents the frequency index that will be used to represent the symbol corresponding to the hexadecimal number F1E4B0F.

Using the first hexadecimal number as an example of mapping to a particular frequency index, the decimal value of Fh is 15. Because position four of each critical band pair is reserved for non-data information, the value of any hexadecimal digit greater than four is incremented by the value of one decimal. Thus, the 15 becomes a 16. The 16 is thus designated (as shown with the asterisk in FIG. 10) as being the code frequency component in the first critical band pair to represent the symbol corresponding to the hexadecimal number F1E4B0F. Though not shown in FIG. 10, the index 1 position (e.g., the second position from the far left in the critical band 7 would be used to represent the hexadecimal number F1E4B0F.

After assigning the representative code frequencies (block 812), the numbers are filled into a LUT (block 814).

Of course, the systems and processes described in conjunction with FIGS. 8-10 are only examples that may be used to generate LUTs having desired properties in conjunction the encoding and decoding systems described herein. Other configurations and processes may be used.

Audio Decoding

In general, the decoder 116 detects a code signal that was inserted into received audio to form encoded audio at the encoder 102. That is, the decoder 116 looks for a pattern of emphasis in code frequencies it processes. Once the decoder 116 has determined which of the code frequencies have been emphasized, the decoder 116 determines, based on the emphasized code frequencies, the symbol present within the encoded audio. The decoder 116 may record the symbols, or may decode those symbols into the codes that were provided to the encoder 102 for insertion into the audio.

In one implementation, the example decoder 116 of FIG. 11 may be implemented using, for example, a digital signal processor programmed with instructions to implement components of the decoder 116. Of course, any other implementation of the example decoder 116 is possible. For example, the decoder 116 may be implemented using one or more processors, programmable logic devices, or any suitable combination of hardware, software, and firmware.

As shown in FIG. 11, an example decoder 116 includes a sampler 1102, which may be implemented using an analog to digital converter (A/D) or any other suitable technology, to which encoded audio is provided in analog format. As shown in FIG. 1, the encoded audio may be provided by a wired or wireless connection to the receiver 110. The sampler 1102 samples the encoded audio at, for example, a sampling frequency of 8 KHz. Of course, other sampling frequencies may be advantageously selected in order to increase resolution or reduce the computational load at the time of decoding. At a sampling frequency of 8 KHz, the Nyquist frequency is 4 KHz and, therefore, all of the embedded code signal is preserved because its spectral frequencies are lower than the Nyquist frequency. The 9216-sample FFT long block length at 48 KHz sampling rate is reduced to 1536 samples at 8 KHz sampling rate. However even at this modified DFT block size, the code frequency indices are identical to the original encoding frequencies and range from 180 to 656.

The samples from the sampler 1102 are provided to a stacker 1104. In general, the stacker 1104 accentuates the code signal in the audio signal information by taking advantage of the fact that messages are repeated or substantially repeated (e.g., only the least significant bits are changed) for a period of time. For example, 42 bits (226 of FIG. 2) of the 49 bits (226 and 224) of the previously described example message of FIG. 2 remain constant for 64 seconds (32 2-second message intervals) when the 42 bits of data 226 in the message include a station identifier and a coarse time stamp which increments once every 64 seconds. The variable data in the last 7 bit group 232 represents time increments in seconds and, thus, varies from message to message. The example stacker 1104 aggregates multiple blocks of audio signal information to accentuate the code signal in the audio signal information. In an example implementation, the stacker 1104 comprises a buffer to store multiple samples of audio information. For example, if a complete message is embedded in two seconds of audio, the buffer may be twelve seconds long to store six messages. The example stacker 1104 additionally comprises an adder to sum the audio signal information associated with the six messages and a divider to divide the sum by the number of repeated messages selected (e.g., six).

By way of example, a watermarked signal y(t) can be represented by the sum of the host signal x(t) and watermark w(t):

y(t)=x(t)+w(t)

In the time domain, watermarks may repeat after a known period T:

w(t)=w(t−T)

According to an example stacking method, the input signal y(t) is replaced by a stacked signal S(t):

${S(t)} = \frac{{y(t)} + {y\left( {t - T} \right)} + \ldots + {y\left( {t - {\left( {n - 1} \right)T}} \right)}}{n}$

In the stacked signal S(t), the contribution of the host signal decreases because the values of samples x(t), x(t−T), . . . , x(t−nT) are independent if the period T is sufficiently large. At the same time, the contribution of the watermarks being made of, for example, in-phase sinusoids, is enhanced.

${S(t)} = {\frac{{x(t)} + {x\left( {t - T} \right)} + \ldots + {x\left( {t - {\left( {n - 1} \right)T}} \right)}}{n} + {w(t)}}$

Assuming x(t), x(t−T), . . . , x(t−nT) are independent random variables drawn from the same distribution X with zero mean E[X]=0 we obtain:

$\left. {\lim\limits_{n\rightarrow\infty}{E\left\lbrack \frac{{x(t)} + {x\left( {t - T} \right)} + \ldots + {x\left( {t - {\left( {n - 1} \right)T}} \right)}}{n} \right\rbrack}}\rightarrow 0 \right.,{and}$ ${{Var}\left\lbrack \frac{{x(t)} + {x\left( {t - T} \right)} + \ldots + {x\left( {t - {\left( {n - 1} \right)T}} \right)}}{n} \right\rbrack} = \frac{{Var}(X)}{n}$

Accordingly, the underlying host signal contributions x(t), . . . , x(t−nT) will effectively be canceling each other while the watermark is unchanged allowing the watermark to be more easily detected.

In the illustrated example, the power of the resulting signal decreases linearly with the number of stacked signals n. Therefore, averaging over independent portions of the host signal can reduce the effects of interference. The watermark is not affected because it will always be added in-phase.

An example process for implementing the stacker 1104 is described in conjunction with FIG. 12.

The decoder 116 may additionally include a stacker controller 1106 to control the operation of the stacker 1104. The example stacker controller 1106 receives a signal indicating whether the stacker 1104 should be enabled or disabled. For example, the stacker controller 1106 may receive the received audio signal and may determine if the signal includes significant noise that will distort the signal and, in response to the determination, cause the stacker to be enabled. In another implementation, the stacker controller 1106 may receive a signal from a switch that can be manually controlled to enable or disable the stacker 1104 based on the placement of the decoder 116. For example, when the decoder 116 is wired to the receiver 110 or the microphone 120 is placed in close proximity to the speaker 114, the stacker controller 1106 may disable the stacker 1104 because stacking will not be needed and will cause corruption of rapidly changing data in each message (e.g., the least significant bits of a timestamp). Alternatively, when the decoder 116 is located at a distance from the speaker 114 or in another environment where significant interference may be expected, the stacker 1104 may be enabled by the stacker controller 1106. Of course, any type of desired control may be applied by the stacker controller 1106.

The output of the stacker 1104 is provided to a time to frequency domain converter 1108. The time to frequency domain converter 1108 may be implemented using a discrete Fourier transformation (DFT), or any other suitable technique to convert time-based information into frequency-based information. In one example, the time to frequency domain converter 1108 may be implemented using a sliding long block fast Fourier transform (FFT) in which a spectrum of the code frequencies of interest is calculated each time eight new samples are provided to the example time to time to frequency domain converter 1108. In one example, the time to frequency domain converter 1108 uses 1,536 samples of the encoded audio and determines a spectrum therefrom using 192 slides of eight samples each. The resolution of the spectrum produced by the time to frequency domain converter 1108 increases as the number of samples used to generate the spectrum is increased. Thus, the number of samples processed by the time to frequency domain converter 1108 should match the resolution used to select the indices in the tables of FIGS. 3-5.

The spectrum produced by the time to frequency domain converter 1108 passes to a critical band normalizer 1110, which normalizes the spectrum in each of the critical bands. In other words, the frequency with the greatest amplitude in each critical band is set to one and all other frequencies within each of the critical bands are normalized accordingly. For example, if critical band one includes frequencies having amplitudes of 112, 56, 56, 56, 56, 56, and 56, the critical band normalizer would adjust the frequencies to be 1, 0.5, 0.5, 0.5, 0.5, 0.5, and 0.5. Of course, any desired maximum value may be used in place of one for the normalization. The critical band normalizer 1110 outputs the normalized score for each of the frequencies of the interest.

The spectrum of scores produced by the critical band normalizer 1110 is passed to the symbol scorer 1112, which calculates a total score for each of the possible symbols in the active symbol table. In an example implementation, the symbol scorer 1112 iterates through each symbol in the symbol table and sums the normalized score from the critical band normalizer 1110 for each of the frequencies of interest for the particular symbol to generate a score for the particular symbol. The symbol scorer 1112 outputs a score for each of the symbols to the max score selector 1114, which selects the symbol with the greatest score and outputs the symbol and the score.

The identified symbol and score from the max score selector 1114 are passed to the comparator 1116, which compares the score to a threshold. When the score exceeds the threshold, the comparator 1116 outputs the received symbol. When the score does not exceed the threshold, the comparator 1116 outputs an error indication. For example, the comparator 1116 may output a symbol indicating an error (e.g., a symbol not included in the active symbol table) when the score does not exceed the threshold. Accordingly, when a message has been corrupted such that a great enough score (i.e., a score that does not exceed the threshold) is not calculated for a symbol, an error indication is provided. In an example implementation, error indications may be provided to the stacker controller 1106 to cause the stacker 1104 to be enabled when a threshold number of errors are identified (e.g., number of errors over a period of time, number of consecutive errors, etc.).

The identified symbol or error from the comparator 1116 is passed to the circular buffers 1118 and the pre-existing code flag circular buffers 1120. An example implementation of the standard buffers 1118 is described in conjunction with FIG. 15. The example circular buffers 1118 comprise one circular buffer for each slide of the time domain to frequency domain converter 1108 (e.g., 192 buffers). Each circular buffer of the circular buffers 1118 includes one storage location for the synchronize symbol and each of the symbol blocks in a message (e.g., eight block messages would be stored in eight location circular buffers) so that an entire message can be stored in each circular buffer. Accordingly, as the audio samples are processed by the time domain to frequency domain converter 1108, the identified symbols are stored in the same location of each circular buffer until that location in each circular buffer has been filled. Then, symbols are stored in the next location in each circular buffer. In addition to storing symbols, the circular buffers 1118 may additionally include a location in each circular buffer to store a sample index indicating the sample in the audio signal that was received that resulted in the identified symbol.

The example pre-existing code flag circular buffers 1120 are implemented in the same manner as the circular buffers 1118, except the pre-existing code flag circular buffers 1120 include one location for the pre-existing code flag synchronize symbol and one location for each symbols in the pre-existing code flag message (e.g., an pre-existing code flag synchronize that includes one message symbol would be stored in two location circular buffers). The pre-existing code flag circular buffers 1120 are populated at the same time and in the same manner as the circular buffers 1118.

The example message identifier 1122 analyzes the circular buffers 1118 and the pre-existing code flag circular buffers 1120 for a synchronize symbol. For example, the message identifier 1122 searches for a synchronize symbol in the circular buffers 1118 and a pre-existing code flag synchronize symbol in the pre-existing code flag circular buffers 1120. When a synchronize symbol is identified, the symbols following the synchronize symbol (e.g., seven symbols after a synchronize symbol in the circular buffers 1118 or one symbol after an pre-existing code flag synchronize symbol in the pre-existing code flag circular buffers 1120) are output by the message identifier 1122. In addition, the sample index identifying the last audio signal sample processed is output.

The message symbols and the sample index output by the message identifier 1122 are passed to the validator 1124, which validates each message. The validator 1124 includes a filter stack that stores several consecutively received messages. Because messages are repeated (e.g., every 2 seconds or 16,000 samples at 8 KHz), each message is compared with other messages in the filter stack that are separated by approximately the number of audio samples in a single message to determine if a match exists. If a match or substantial match exists, both messages are validated. If a message cannot be identified, it is determined that the message is an error and is not emitted from the validator 1124. In cases where messages might be affected by noise interference, messages might be considered a match when a subset of symbols in a message match the same subset in another already validated message. For example, if four of seven symbols in a message match the same four symbols in another message that has already been validated, the message can be identified as partially validated. Then, a sequence of the repeated messages can be observed to identify the non-matching symbols in the partially validated message.

The validated messages from the validator 1124 are passed to the symbol to bit converter 1126, which translates each symbol to the corresponding data bits of the message using the active symbol table.

An example decoding process 1200 is shown in FIG. 12. The example process 1200 may be carried out by the example decoder 116 shown in FIG. 11, or by any other suitable decoder. The example process 1200 begins by sampling audio (block 1202). The audio may be obtained via an audio sensor, a hardwired connection, via an audio file, or through any other suitable technique. As explained above the sampling may be carried out at 8,000 Hz, or any other suitable frequency.

As each sample is obtained, the sample is aggregated by a stacker such as the example stacker 1104 of FIG. 11 (block 1204). An example process for performing the stacking is described in conjunction with FIG. 13.

The new stacked audio samples from the stacker process 1204 are inserted into a buffer and the oldest audio samples are removed (block 1206). As each sample is obtained, a sliding time to frequency conversion is performed on a collection of samples including numerous older samples and the newly added sample obtained at blocks 1202 and 1204 (block 1208). In one example, a sliding FFT may be used to process streaming input samples including 9215 old samples and the one newly added sample. In one example, the FFT using 9216 samples results in a spectrum having a resolution of 5.2 Hz.

After the spectrum is obtained through the time to frequency conversion (block 1208), the transmitted symbol is determined (block 1210). An example process for determining the transmitted symbol is described in conjunction with FIG. 14.

After the transmitted message is identified (block 1210), buffer post processing is performed to identify a synchronize symbol and corresponding message symbols (block 1212). An example process for performing post-processing is described in conjunction with FIG. 15.

After post processing is performed to identify a transmitted message (block 1212), message validation is performed to verify the validity of the message (block 1214). An example process for performing the message validation is described in conjunction with FIG. 18.

After a message has been validated (block 1214), the message is converted from symbols to bits using the active symbol table (block 1216). Control then returns to block 1106 to process the next set of samples.

FIG. 13 illustrates an example process for stacking audio signal samples to accentuate an encoded code signal to implement the stack audio process 1204 of FIG. 12. The example process may be carried out by the stacker 1104 and the stacker controller 1106 of FIG. 11. The example process begins by determining if the stacker control is enabled (block 1302). When the stacker control is not enabled, no stacking is to occur and the process of FIG. 13 ends and control returns to block 1206 of FIG. 12 to process the audio signal samples unstacked.

When the stacker control is enabled, newly received audio signal samples are pushed into a buffer and the oldest samples are pushed out (block 1304). The buffer stores a plurality of samples. For example, when a particular message is repeatedly encoded in an audio signal every two seconds and the encoded audio is sampled at 8 KHz, each message will repeat every 16,000 samples so that buffer will store some multiple of 16,000 samples (e.g., the buffer may store six messages with a 96,000 sample buffer). Then, the stacker 1108 selects substantially equal blocks of samples in the buffer (block 1306). The substantially equal blocks of samples are then summed (block 1308). For example, sample one is added to samples 16,001, 32,001, 48,001, 64,001, and 80,001, sample two is added to samples 16,002, 32,002, 48,002, 64,002, 80,002, sample 16,000 is added to samples 32,000, 48,000, 64,000, 80,000, and 96,000.

After the audio signal samples in the buffer are added, the resulting sequence is divided by the number of blocks selected (e.g., six blocks) to calculate an average sequence of samples (e.g., 16,000 averaged samples) (block 1310). The resulting average sequence of samples is output by the stacker (block 1312). The process of FIG. 13 then ends and control returns to block 1206 of FIG. 12.

FIG. 14 illustrates an example process for implementing the symbol determination process 1210 after the received audio signal has been converted to the frequency domain. The example process of FIG. 14 may be performed by the decoder 116 of FIGS. 1 and 11. The example process of FIG. 14 begins by normalizing the code frequencies in each of the critical bands (block 1402). For example, the code frequencies may be normalized so that the frequency with the greatest amplitude is set to one and all other frequencies in that critical band are adjusted accordingly. In the example decoder 116 of FIG. 11, the normalization is performed by the critical band normalizer 1110.

After the frequencies of interest have been normalized (block 1402). The example symbol scorer 1112 selects the appropriate symbol table based on the previously determined synchronization table (block 1404). For example, a system may include two symbol tables: one table for a normal synchronization and one table for a pre-existing code flag synchronization. Alternatively, the system may include a single symbol table or may include multiple synchronization tables that may be identified by synchronization symbols (e.g., cross-table synchronization symbols). The symbol scorer 1112 then computes a symbol score for each symbol in the selected symbol table (block 1406). For example, the symbol scorer 1112 may iterate across each symbol in the symbol table and add the normalized scores for each of the frequencies of interest for the symbol to compute a symbol score.

After each symbol is scored (block 1406), the example max score selector 1114 selects the symbol with the greatest score (block 1408). The example comparator 1116 then determines if the score for the selected symbol exceeds a maximum score threshold (block 1410). When the score does not exceed the maximum score threshold, an error indication is stored in the circular buffers (e.g., the circular buffers 1118 and the pre-existing code flag circular buffers 1120) (block 1412). The process of FIG. 14 then completes and control returns to block 1212 of FIG. 12.

When the score exceeds the maximum score threshold (block 1410), the identified symbol is stored in the circular buffers (e.g., the circular buffers 1118 and the pre-existing code flag circular buffers 1120) (block 1414). The process of FIG. 14 then completes and control returns to block 1212 of FIG. 12.

FIG. 15 illustrates an example process for implementing the buffer post processing 1212 of FIG. 12. The example process of FIG. 15 begins when the message identifier 1122 of FIG. 11 searches the circular buffers 1118 and the circular buffers 1120 for a synchronization indication (block 1502).

For example, FIG. 16 illustrates an example implementation of circular buffers 1118 and FIG. 17 illustrates an example implementation of pre-existing code flag circular buffers 1120. In the illustrated example of FIG. 16, the last location in the circular buffers to have been filled is location three as noted by the arrow. Accordingly, the sample index indicates the location in the audio signal samples that resulted in the symbols stored in location three. Because the line corresponding to sliding index 37 is a circular buffer, the consecutively identified symbols are 128, 57, 22, 111, 37, 23, 47, and 0. Because 128 in the illustrated example is a synchronize symbol, the message can be identified as the symbols following the synchronize symbol. The message identifier 1122 would wait until 7 symbols have been located following the identification of the synchronization symbol at sliding index 37.

The pre-existing code flag circular buffers 1120 of FIG. 17 include two locations for each circular buffer because the pre-existing code flag message of the illustrated example comprises one pre-existing code flag synchronize symbol (e.g., symbol 254) followed by a single message symbol. According to the illustrated example of FIG. 2, the pre-existing code flag data block 230 is embedded in two long blocks immediately following the 7 bit timestamp long block 228. Accordingly, because there are two long blocks for the pre-existing code flag data and each long block of the illustrated example is 1,536 samples at a sampling rate of 8 KHz, the pre-existing code flag data symbol will be identified in the pre-existing code flag circular buffers 3072 samples after the original message. In the illustrated example FIG. 17, sliding index 37 corresponds to sample index 38744, which is 3072 samples later than sliding index 37 of FIG. 16 (sample index 35672). Accordingly, the pre-existing code flag data symbol 68 can be determined to correspond to the message in sliding index 37 of FIG. 16, indicating that the message in sliding index 37 of FIG. 16 identifies an original encoded message (e.g., identifies an original broadcaster of audio) and the sliding index 37 identifies an pre-existing code flag message (e.g., identifies a re-broadcaster of audio).

Returning to FIG. 12, after a synchronize or pre-existing code flag synchronize symbol is detected, messages in the circular buffers 1118 or the pre-existing code flag circular buffers 1120 are condensed to eliminate redundancy in the messages. For example, as illustrated in FIG. 16, due to the sliding time domain to frequency domain conversion and duration of encoding for each message, messages are identified in audio data for a period of time (sliding indexes 37-39 contain the same message). The identical messages in consecutive sliding indexes can be condensed into a single message because they are representative of only one encoded message. Alternatively, condensing may be eliminated and all messages may be output when desired. The message identifier 1122 then stores the condensed messages in a filter stack associated with the validator 1124 (block 1506). The process of FIG. 15 then ends and control returns to block 1214 of FIG. 12.

FIG. 18 illustrates an example process to implement the message validation process 1214 of FIG. 12. The example process of FIG. 12 may be performed by the validator 1124 of FIG. 11. The example process of FIG. 18 begins when the validator 1124 reads the top message in the filter stack (block 1802).

For example, FIG. 19 illustrates an example implementation of a filter stack. The example filter stack includes a message index, seven symbol locations for each message index, a sample index identification, and a validation flag for each message index. Each message is added at message index M7 and a message at location M0 is the top message that is read in block 1802 of FIG. 18. Due to sampling rate variation and variation of the message boundary within a message identification, it is expected that messages will be separated by samples indexes of multiples of approximately 16,000 samples when messages are repeated every 16,000 samples.

Returning to FIG. 19, after the top message in the filter stack is selected (block 1802), the validator 1124 determines if the validation flag indicates that the message has been previously validated (block 1804). For example, FIG. 19 indicates that message M0 has been validated. When the message has been previously validated, the validator 1124 outputs the message (block 1812) and control proceeds to block 1816.

When the message has not been previously validated (block 1804), the validator 1124 determines if there is another suitably matching message in the filter stack (block 1806). A message may be suitably matching when it is identical to another message, when a threshold number of message symbols match another message (e.g., four of the seven symbols), or when any other error determination indicates that two messages are similar enough to speculate that they are the same. According to the illustrated example, messages can only be partially validated with another message that has already been validated. When a suitable match is not identified, control proceeds to block 1814.

When a suitable match is identified, the validator 1124 determines if a time duration (e.g., in samples) between identical messages is proper (block 1808). For example, when messages are repeated every 16,000 samples, it is determined if the separation between two suitably matching messages is approximately a multiple of 16,000 samples. When the time duration is not proper, control proceeds to block 1814.

When the time duration is proper (block 1808), the validator 1124 validates both messages by setting the validation flag for each of the messages (block 1810). When the message has been validated completely (e.g., an exact match) the flag may indicate that the message is fully validated (e.g., the message validated in FIG. 19). When the message has only been partially validated (e.g., only four of seven symbols matched), the message is marked as partially validated (e.g., the message partially validated in FIG. 19). The validator 1124 then outputs the top message (block 1812) and control proceeds to block 1816.

When it is determined that there is not a suitable match for the top message (block 1806) or that the time duration between a suitable match(es) is not proper (block 1808), the top message is not validated (block 1814). Messages that are not validated are not output from the validator 1124.

After determining not to validate a message (blocks 1806, 1808, and 1814) or outputting the top message (block 1812), the validator 1816 pops the filter stack to remove the top message from the filter stack. Control then returns to block 1802 to process the next message at the top of the filter stack.

While example manners of implementing any or all of the example encoder 102 and the example decoder 116 have been illustrated and described above one or more of the data structures, elements, processes and/or devices illustrated in the drawings and described above may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, the example encoder 102 and example decoder 116 may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware. Thus, for example, the example encoder 102 and the example decoder 116 could be implemented by one or more circuit(s), programmable processor(s), application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)), etc. For example, the decoder 116 may be implemented using software on a platform device, such as a mobile telephone. If any of the appended claims is read to cover a purely software implementation, at least one of the prior code detector 204, the example message generator 210, the symbol selector 212, the code frequency selector 214, the synthesizer 216, the inverse FFT 218, the mixer 220, the overlapping short block maker 240, the masking evaluator 242, the critical band pair definer 702, the frequency definer 704, the number generator 706, the redundancy reducer 708, the excess reducer 710, the code frequency definer 712, the LUT filler 714, the sampler 1102, the stacker 1104, the stacker control 1106, the time domain to frequency domain converter 1108, the critical band normalize 1110, the symbol scorer 1112, the max score selector 1114, the comparator 1116, the circular buffers 1118, the pre-existing code flag circular buffers 1120, the message identifier 1122, the validator 1124, and the symbol to bit converter 1126 are hereby expressly defined to include a tangible medium such as a memory, DVD, CD, etc. Further still, the example encoder 102 and the example decoder 116 may include data structures, elements, processes and/or devices instead of, or in addition to, those illustrated in the drawings and described above, and/or may include more than one of any or all of the illustrated data structures, elements, processes and/or devices.

Having described the operation of example encoding and decoding systems, attention will now be turned to uses or applications of the example encoding and decoding systems. As described below, by way of non-limiting examples, the example encoding and decoding systems may be used for position monitoring within a geographical area, controlling devices, and acoustic measurements.

The example encoding and decoding systems may be used to monitor geographical position or proximity within a geographical area. For example, as shown in FIG. 20, a shopper's position within a store 2002 may be monitored through the use of a smart shopping cart 2004 including a decoder/logger 2006 and an audio sensor 2008. In such an example, the store 2002 may include several departments, such as, for example, a toy department 2010, a sporting goods department 2012, and a hardware department 2014. Each of the departments is equipped with an audio system 2020, 2022, 2024, that presents audio 2026, such as, for example, music that is commonly played in stores.

In each department 2010, 2012, and 2014, the audio 2026 is coupled to an encoder 2030, 2032, 2034, each of which may be implemented using the foregoing described techniques for encoding. In addition to the audio 2026, the encoders 2030, 2032, and 2034 receive codes that correspond to the departments in which the encoders reside. For example, the encoder 2030 in the toy department 2010 receives a toys code 2040, the encoder 2032 in the sporting goods department 2012 receives a sporting goods code 2042, and the encoder 2034 in the hardware department 2014 receives a hardware code 2044. As described above, the encoders 2030, 2032, 2034 combine the audio with their respective codes 2040, 2042, 2044 to produce encoded audio wherein the encoding does not affect the audible quality of the audio 2026 in any manner noticeable to human hearing. The encoded audio is then respectively broadcast in each department 2010, 2012, and 2014 via speakers 2050, 2052, 2053, and 2054.

Thus, the audio played in each department 2010, 2012, 2014 is encoded with a code representing that department. The speakers 2050, 2052, 2053, and 2054 are positioned within each department so as to form audio coverage areas 2060, 2062, and 2064 that generally correspond to the geographical areas of the departments 2010, 2012, 2014. Of course, as shown with respect to the sporting goods department 2012, more than one speaker 2052, 2053 may be used to provide audio coverage that is reasonably tailored to the shape of the department and that does not substantially infringe on other departments.

The audio coverage areas 2060, 2062, 2064 of encoded audio corresponding to the respective departments 2010, 2012, 2014 enables tracking of a user within the store 2002. For example, the smart shopping cart 2004 may be issued to an, as yet, unidentified customer upon that customer entering the store 2002. As the customer walks about the store 2002, the audio sensor 2008 is exposed to various audio sources such as, for example, people talking and other ambient noise. In addition, the audio sensor 2008 is also exposed to audio that is presented by speakers (e.g., the speakers 2050, 2052, 2053, and 2054) in the various departments (e.g., 2010, 2012, and 2014) of the store 2002. As described above, the audio presented by the speakers (e.g., the speakers 2050, 2052, 2053, and 2054) is encoded with one or more codes identifying the department in which the speaker is placed. Thus, when the smart shopping cart 2004 enters, for example, the toy department 2010, the audio sensor 2008 receives audio from the speaker 2050, which includes the toys code 2040. The audio sensor 2008 passes the received audio to the decoder/logger 2006, which identifies the presence of the code in the audio and logs the time at which the code was received. Thus, the decoder/logger 2006 provides data indicative of the fact that the smart cart 2004 was present in the toy department 2010. Based on the frequency with which the toys code 2040 is repeated in the audio presented by the speaker 2050, the decoder/logger 2006 logs data indicative of the time the a user, or at least that user's cart, was in the toy department 2010.

Thus, as the unidentified user pushes his/her smart cart 2004 around the store 2002, the decoder/logger 2006 logs codes that are received and the time at which they were received. Therefore, as a user or shopper traverses from the toy department 2010 to the sporting goods department 2012, the decoder/logger 2006 receives and records the codes indicative of the toy department 2010 and then a change in code from the toys code 2040 to the sporting goods code 2042 to indicate that the shopper moved his/her smart cart 2004 between departments 2010, 2012.

When the shopper or user proceeds to checkout, the codes stored in the decoder/logger 2006, which track the presence of the smart cart 2004 around the store 2002 are retrieved from the decoder/logger 2006 and may be aggregated with data from other smart shopping carts. In addition, if the shopper or user of the smart shopping cart 2004 uses a store card, such as a preferred shopper card, when checking out, the data from the decoder/logger 2006 may be associated with the identity or demographics associated with the store card. In this manner, an association may be made between a particular shopper and/or a demographic profile of a shopper and the time that such a shopper spends in the various areas of the store 2002.

While the foregoing example was described in the context of a smart shopping cart, the decoding and logging functionality need not be implemented using a shopping cart. For example, the functionality decoder/logger 2006 may be implemented in any type of shopping implement a smart shopping basket, a shopping bag, or a portable device that may be issued to persons entering the store. Alternatively, the functionality of the decoder/logger 2006 may be implemented by software that may be installed on any type of electronic device including, for example, a computer, a mobile telephone, a music player, a portable electronic device, etc. Additionally, incentives may be provided to shoppers to incent the shoppers to use smart shopping carts, smart shopping baskets, or any other decoding and logging device. For example, an incentive may be provided to user's who visit a particular location in the store as evidenced by the decoder/logger 2006 associated with the user having received a code associated with the particular location. A coupon may be printed for the user, a coupon may be associated with the user's decoder/logger 2006 so that the coupon is applied to the user's purchase when they reach the cash register, etc.

While the systems shown in FIG. 20 included an encoder into which both audio and codes are provided so that the codes could be embedded in the audio, a different approach may be to mix codes with audio in a free space, as shown in FIG. 21. As shown in FIG. 21, audio 2102 may be provided to a first speaker 2104 and manifest therefrom to provide a coverage area of audio 2106. The audio provided by the speaker 2104 is not encoded audio. However, an audio sensor 2110 may be disposed within the coverage area 2106 and, therefore, senses the amplitude, frequency and other characteristics of the audio in the coverage area 2106.

Signals from the audio sensor 2110 are provided to a code generator 2112, which processes the signals that represent the audio in the coverage area 2106 to assess the ability of such audio to hide or mask code signals from human hearing. Thus, the code generator 2112 may perform some or all of the processing described above in connection with the encoder 102 of FIG. 1. That is, the code generator 2112 determines the masking provided by the ambient audio within the coverage area 2106, some of which is provided by the speaker 2104, and determines a level at which a code signal should be output from the code generator 2112 to a speaker 2114. Thus, a code signal, such as a collection of sine waves at different frequencies designed by, for example, the charts of FIGS. 3-5, is output from the speaker 2114 at a level of sound pressure that is masked by the ambient audio in the coverage area 2106. Alternatively, there may be no speaker 2104 and code signal is masked by the ambient noise such as, for example, people talking, electrical equipment such as fans, blowers, compressors, speakers not associated with the system (e.g., a public address system for a store), etc.

As shown in FIG. 21, the code generator may be preprogrammed with a code, such as a code representing a department of a store, as described above. In other examples, a code may be provided to the code generator 2112 from another source.

Advantageously, the system shown in FIG. 21 may be used in situations in which installation of an encoder in line with audio provided to a speaker is not possible or desirable. That is, the arrangement of FIG. 21 enables the code system to be a standalone system that does not necessarily electrically connect to an existing audio system. Thus, the encoding aspects shown in FIG. 21 may be separately installable into an existing system without disruption thereto.

An additional use of the encoding and decoding systems described above may be in controlling objects or devices via hidden codes that are embedded in an audio signal, as described above. For example, turning to FIG. 22, a system is shown at two different points in time t1 and t2. At both points in time, the system 2200 includes an encoder 2202 receiving audio 2204 and one or both of a first code 2206 and a second code 2208. The encoder 2202 has an output that is coupled to a speaker 2210. The encoder 2202 embeds either the first code 2206 or the second code 2208 into the audio 2204 and, thus, produces audio from the speaker 2210 having either the first code 2206 or the second code 2208 embedded therein. In the example, of FIG. 22, the encoder 2202 encodes the first code 2206 into the audio 2204 at time t1. As noted above, the first code 2206 and the second code 2208 may be provided to the encoder 2202 and the encoder 2202 may select which code to embed into the audio 2204 based on timing or another criterion. Alternatively, at time t1, only the first code 2206 may be provided to the encoder 2202.

At time t1, an audio sensor 2220 receives the audio, which includes the first code 2206 embedded therein, from the speaker 2210. An electrical signal from the audio sensor 2220 is provided to the decoder 2222 in which the electrical signal is processed to determine if codes are embedded therein. If the decoder 2222 determines that codes are present, the codes are obtained and provided to a controller 2224. In response to receiving the first code 2206 from the decoder 2222, the controller 2224 provides signals to a device 2226 to control the device 2226. For example, in response to receiving the first code 2206 from the decoder 2222, the controller 2224 may control the device 2226 to manifest an advertisement for an item of interest to men. For example, the device 2226 may be an advertisement display device that is capable of showing multiple, different advertisements. The different advertisements may be displayed by changing or scrolling paper advertisement, or the advertisements may be video or audio commercials that are manifest on the device 2226.

According to the example, at time t2, however, the encoder 2202 encodes the second code 2208 into the audio 2204 and, thus, audio from the speaker 2210 and includes the second code 2208 hidden therein. In response to receiving the audio having the second code 2208 therein, the decoder 2222 obtains the second code 2208 and provides the same to the controller 2224, which in turn, manifests on the device 2226 an advertisement that is generally targeted toward female shoppers.

The foregoing system described in conjunction with FIG. 22 is flexible in that, for example, advertisements throughout a store could be altered in response to various criteria. For example, when announcing a special on shovels over the speaker system of the store, a third code could be used and all receivers of that code could cause display of shovels on advertising devices located throughout the store. In this manner, previously passive advertisements can be made flexible and tied to an overall advertising plan for the store, which may include coordinated audio announcements and the like.

Flowcharts representative of example machine readable instructions that may be executed to implement some or all of the elements of the system 100, the blocks illustrated in FIGS. 20-22, or any other systems described herein are shown in FIGS. 23-25.

In these examples, the machine readable instructions represented by each flowchart may be implemented by one or more programs, routines, or processes, and may be executed by: (a) a processor, such as the microprocessor 2705 shown in the example computer 2700 discussed below in connection with FIG. 27, (b) a controller, and/or (c) any other suitable device. The one or more programs may be embodied in software stored on a tangible medium such as, for example, a flash memory, a CD-ROM, a floppy disk, a hard drive, a DVD, or a memory associated with the processor 2705, but the entire program or programs and/or portions thereof could alternatively be executed by a device other than the microprocessor 2705 and/or embodied in firmware or dedicated hardware (e.g., implemented by an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable logic device (FPLD), discrete logic, etc.). For example, any one, some or all of the example system 100 including the encoder 102, the decoder 104, or any blocks illustrated in FIGS. 23-25 could be implemented by any combination of software, hardware, and/or firmware. Also, some or all of the processes represented by the flowcharts of FIGS. 20-22 may be implemented manually.

FIG. 23 is a flowchart of an example process that may be performed to implement the decoder/logger 2006 of FIG. 20. The example process begins when decoder/logger 2006 receives an audio signal via the audio sensor 2008 (block 2302). For example, the decoder/logger 2006 may be attached to a shopping cart in a grocery store, installed on a personal mobile device such as a mobile telephone, etc. The decoder/logger 2006 may, for example, receive ambient audio that includes music embedded with a code that is played in the grocery store. The decoder/logger 2006 then attempts to decode a code embedded in the audio signal (block 2304). Next, the decoder/logger 2006 determines if a valid code was detected and decoded (block 2306). If a valid code was not detected, control returns to block 2302 to receive an audio signal. Alternatively, the decoder/logger 2006 may continue receiving audio to a buffer while code detection is performed or decoding may be performed in any other parallel manner.

When a valid code is detected (block 2306), the decoder/logger 2006 stores the decoded code and a timestamp in a memory of the decoder/logger 2006. Alternatively, the decoder/logger 2006 may transmit the decoded code to a remote location. The transmission may include a unique or semi-unique identification of the decoder/logger 2006. Control then returns to block 2302.

FIG. 24 is a flowchart of an example process that may be performed after the decoder/logger 2006 has logged one or more codes. The example process begins when a data retrieval device receives a shopper identification (block 2402). For example, the data retrieval device may be integrated with a store checkout device such as a cash register, may be a device attached to a cash register, may be a standalone device, etc. As described in conjunction with FIG. 26, a shopper may present an identification when completing their purchase at a cash register of a store. The shopper identification may be in any form, including an identification associated with a savings program at a store, a government issued identification number, an identification number or code issued by a monitoring company, etc. Alternatively, where no association of a shopper and tracking data is required, no identification number may be received and the process may begin at block 2404.

Next, purchase information is received at the data retrieval device (block 2404). Purchase information may include any information about a purchase made by a shopper. For example, the purchase information may include product identifiers, price identifiers, product quantities, coupon information, etc. The data retrieval device then receives logged data from the decoder/logger 2006 associated with the shopper (block 2406). For example, the data retrieval device may receive the logged data via a wireless communication, a wired communication, etc. Alternatively, the data retrieval device may receive an identifier for the decoder/logger 2006 where the logged data is separately received or retrieved (e.g., where the decoder/logger 2006 transmits logged data to a data collection facility or location). The data retrieval device then stores the logged data and purchase information in association with the shopper identifier (block 2408). For example, the data retrieval device may store the information in a local memory, may transmit the data to a data collection facility or location, etc. The data may be stored or transmitted in any format such as, for example, in a table, in a database, in a file, in a record, etc.

While the process of FIG. 24 includes receiving a shopper identifier and purchase information in addition to logged data, only the log data may be retrieved in some implementations. In addition, while the shopper identifier, purchase information, and logged data are described as being retrieved at a single location in FIG. 24, all or some of the information may be received or retrieved at separate locations.

FIG. 25 is a flowchart of an example process that may implement the example code generator 2112. The example process of FIG. 25 begins when the code generator 2112 receives an ambient audio signal via the audio sensor 2110 (block 2502). For example, the ambient audio signal may include audio output by the speaker 2104 or any other audio or sound in the area of the audio sensor 2110. The code generator 2112 of the illustrated example then determines characteristics of the received audio signal (block 2504). The determined characteristics may include the amplitude of the audio signal, the amplitude of one or more frequencies of the audio signal, etc. The code generator 2112 then receives a code that is to be embedded in the audio signal (block 2506). For example, the code may be input by a user, may be received from a network connection, may be received from an attached device, etc. In an example implementation, the code may be received from an advertisement source that presents or controls audio and/or video advertisements so that the code can be output in coordination with the advertisement.

According to the illustrated example, the code generator 2112 then determines masking characteristics based on the determined audio characteristics (block 2508). The masking characteristics can be used when generating an audio signal for outputting the code so that the audio signal is disguised from human hearing. For example, the masking characteristics may be analyzed as described in conjunction with the masking evaluator 242 of FIG. 2. Then, using the masking characteristics, an audio signal is generated with the code embedded therein (block 2510). For example, as described in conjunction with the encoder 104, sine waves emphasizing the frequencies associated with the code (e.g., the frequencies identified in FIGS. 3-5) may be generated and mixed. The generated audio signal is then output by the speaker 2114. Accordingly, an audio signal including the code is output and can be detected by devices that are listening to the ambient audio nearby (e.g., the decoder/logger 2006 or the decoder 2222). The output audio signal is mixed in the air with the ambient audio. In an example implementation, when the amplitude of the ambient audio is low, the output audio signal is of low amplitude and when the amplitude of the ambient audio is high, the output audio signal is of high amplitude.

FIG. 26 is a flowchart of an example usage scenario for the system of FIG. 20. The example usage scenario begins when a user enters a store and selects a shopping basket (block 2602). According to the illustrated example, the shopping basket includes the decoder/logger 2006). Alternatively, the decoder/logger 2006 may be in another location. For example, the decoder/logger 2006 could be installed on a user's mobile phone.

The user moves the basket (or other apparatus including the decoder/logger 2006) near a first location (block 2604). According to the illustrated example, the first location includes a speaker that outputs an audio signal including a first embedded code. The decoder/logger 2006 in the shopping basket receives the audio that includes the first embedded code (block 2606). The embedded code is extracted and stored in the decoder/logger 2006 as described in conjunction with FIG. 23.

The user then moves the basket near a second location (block 2608). According to the illustrated example, the second location includes a speaker that outputs an audio signal including a second embedded code. The decoder/logger 2006 in the shopping basket receives the audio that includes the first embedded code (block 2610). The embedded code is extracted and stored in the decoder/logger 2006.

The user then moves the basket to the checkout to purchase selected store items (block 2612). At the checkout, the memory of the decoder/logger 2006 is retrieved by a data retrieval device (block 2614). For example, the decoder/logger 2006 may transmit its memory to the data retrieval device via a wired or wireless communication connection. The user then presents an identification (block 2616). For example, the user may provide a government issued identification, a credit card, a bank card, a check, a shopper identifier, etc. In an example implementation, the identification may be previously known to the business performing the monitoring and may be associated with demographic information, previous purchase information, etc. about the user.

Then, the products selected by the user for purchase are processed at the checkout to complete the purchase and to gather information about the purchase for storage (block 2618). The logged information, the user identification, and the purchase information are stored together in a memory (block 2620). For example, the information may be transmitted to a local or remote data collection facility. The data can then be analyzed to determine information about the user's actions. For example the location or purchased items can be compared with the logged data to determine from which of several possible locations the user selected the item for purchasing. In addition, the logged data can be analyzed without reference to the purchase or user identification to see how a user moves throughout the store. While a single user moving throughout a store is illustrated in FIG. 26, the usage scenario may be repeated several times as multiple users visit the store. Additionally, the principles used in the usage scenario may take place at any type of location such as, for example, a grocery store, a home supply store, a museum, a book store, a government building, a park, etc.

While example manners of implementing the processes and usage scenarios of FIGS. 23-26 have been illustrated, one or more of the elements, processes and/or devices illustrated in FIGS. 23-26 may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, the example encoder 2030, the example encoder 2032, the example encoder 2034, the example decoder/logger 2006, the example code generator 2112, the example encoder 2202, the example decoder 2222, the example controller 2224, or any other block or component may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware. Thus, for example, any of the example encoder 2030, the example encoder 2032, the example encoder 2034, the example decoder/logger 2006, the example code generator 2112, the example encoder 2202, the example decoder 2222, the example controller 2224, or any other block or component could be implemented by one or more circuit(s), programmable processor(s), application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)), etc. When any of the appended apparatus claims are read to cover a purely software and/or firmware implementation, at least one of the example encoder 2303, the example decoder/logger 2006, the example code generator 2112, the example encoder 2202, the example decoder 2222, the example controller 2224, or any other block or component are hereby expressly defined to include a tangible medium such as a memory, DVD, CD, etc. storing the software and/or firmware. Further still, the example encoder 2303, the example decoder/logger 2006, the example code generator 2112, the example encoder 2202, the example decoder 2222, the example controller 2224, or any other block or component may include one or more elements, processes and/or devices in addition to, or instead of, those illustrated in FIGS. 23-26, and/or may include more than one of any or all of the illustrated elements, processes and devices.

FIG. 27 is a schematic diagram of an example processor platform 2700 that may be used and/or programmed to implement any or all of the example encoder 102, the decoder 116, the encoder 2030, the encoder 2032, the encoder 2034, the code generator 2012, the encoder 2102, the decoder 2122, the controller 2124, and/or any other component described herein. For example, the processor platform 2700 can be implemented by one or more general purpose processors, processor cores, microcontrollers, etc. Additionally, the processor platform 2700 may be implemented as a part of a device having other functionality. For example, the processor platform 2700 may be implemented using processing power provided in a mobile telephone, or any other handheld device.

The processor platform 2700 of the example of FIG. 27 includes at least one general purpose programmable processor 2705. The processor 2705 executes coded instructions 2710 and/or 2712 present in main memory of the processor 2705 (e.g., within a RAM 2715 and/or a ROM 2720). The processor 2705 may be any type of processing unit, such as a processor core, a processor and/or a microcontroller. The processor 2705 may execute, among other things, example machine accessible instructions implementing the processes described herein. The processor 2705 is in communication with the main memory (including a ROM 2720 and/or the RAM 2715) via a bus 2725. The RAM 2715 may be implemented by DRAM, SDRAM, and/or any other type of RAM device, and ROM may be implemented by flash memory and/or any other desired type of memory device. Access to the memory 2715 and 2720 may be controlled by a memory controller (not shown).

The processor platform 2700 also includes an interface circuit 2730. The interface circuit 2730 may be implemented by any type of interface standard, such as a USB interface, a Bluetooth interface, an external memory interface, serial port, general purpose input/output, etc. One or more input devices 2735 and one or more output devices 2740 are connected to the interface circuit 2730.

Although certain example apparatus, methods, and articles of manufacture are described herein, other implementations are possible. The scope of coverage of this patent is not limited to the specific examples described herein. On the contrary, this patent covers all apparatus, methods, and articles of manufacture falling within the scope of the invention. 

1. A method for tracking a shopper, the method comprising: receiving a first audio signal at a first location with a decoder attached to a shopping implement; determining a first code encoded in the first audio signal; receiving a second audio signal at a second location with the decoder; determining a second code encoded in the first audio signal; and transmitting the first code and the second code to a data retrieval device.
 2. A method as defined in claim 1, wherein the data retrieval device is integrated in a store checkout device.
 3. A method as defined in claim 1, further comprising determining that the shopping implement was at the first location based on receiving the first code from the shopping implement.
 4. A method as defined in claim 1, further comprising receiving an identification of a person associated with the shopping implement.
 5. A method as defined in claim 1, wherein the shopping implement is at least one of a shopping cart, a shopping basket, a shopping bag, or a portable electronic device.
 6. A method as defined in claim 1, wherein the data retrieval device is a store checkout device.
 7. A method as defined in claim 1, further comprising: receiving a shopper identification; receiving purchase information; and storing the first code, the second code, and the purchase information in association with the shopper identification.
 8. A system for tracking a shopper, the system comprising: a decoder attached to a shopping implement to receive a first audio signal at a first location, determine a first code encoded in the first audio signal, receive a second audio signal at a second location with the decoder, and determine a second code encoded in the first audio signal, and transmit the first code and the second code to a data retrieval device; and the data retrieval device to receive the first code and the second code and to store the first code and the second code.
 9. A system as defined in claim 8, wherein the data retrieval device is integrated in a store checkout device.
 10. A system as defined in claim 8, wherein the data retrieval device is further to determine that the shopping implement was at the first location based on receiving the first code from the shopping implement.
 11. A system as defined in claim 8, wherein the data retrieval device is further to receive an identification of a person associated with the shopping implement.
 12. A system as defined in claim 8, wherein the shopping implement is at least one of a shopping cart, a shopping basket, a shopping bag, or a portable electronic device.
 13. A system as defined in claim 8, wherein the data retrieval device is a store checkout device.
 14. A system as defined in claim 8, wherein the data retrieval device is further to: receive a shopper identification; receive purchase information; and store the first code, the second code, and the purchase information in association with the shopper identification.
 15. A machine readable medium storing instructions that, when executed, cause a computer to track a shopper by: receiving a first audio signal at a first location with a decoder attached to a shopping implement; determining a first code encoded in the first audio signal; receiving a second audio signal at a second location with the decoder; determining a second code encoded in the first audio signal; and transmitting the first code and the second code to a data retrieval device.
 16. A machine readable medium as defined in claim 15, wherein the data retrieval device is integrated in a store checkout device.
 17. A machine readable medium as defined in claim 15, wherein the instructions further cause the computer to determine that the shopping implement was at the first location based on receiving the first code from the shopping implement.
 18. A machine readable medium as defined in claim 15, wherein the instructions further cause the computer to receive an identification of a person associated with the shopping implement.
 19. A machine readable medium as defined in claim 15, wherein the shopping implement is at least one of a shopping cart, a shopping basket, a shopping bag, or a portable electronic device.
 20. A machine readable medium as defined in claim 15, wherein the data retrieval device is a store checkout device. 21-39. (canceled) 